<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
<HEAD>

<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
<TITLE>
Expanding the Ant classpath
</TITLE>

<link rel="stylesheet" type="text/css" HREF="../book.css">
</HEAD>
<BODY BGCOLOR="#ffffff">
<h2>
Expanding the Ant classpath</h2>
<p>Plug-ins can contribute 
<a href="../reference/extension-points/org_eclipse_ant_core_extraClasspathEntries.html">extra JAR files</a> 
to the Ant classpath. The plug-in contributing the JARs is added to the Ant classpath, and as a result,
classes inside the contributed JAR files will have access to all classes available to the plug-in. However, the 
reverse is not true. Since the contributed JAR files must be separate JARs, and not plug-in libraries,
the plug-in classes do not have access to the classes provided by the contributed JARs. The
<a href="../reference/extension-points/org_eclipse_ant_core_extraClasspathEntries.html">
<b>org.eclipse.ant.core.extraClasspathEntries</b></a> extension point provides an example of how to specify the extra JARs 
in the plugin.xml file.</p>
</BODY></HTML>